GetEvents gets all LogEvent records associated with this job. The data is refreshed from the server if necessary to get the latest information. 

Log messages are purged when the instance with which they are associated is purged, based on the job's HistoryRetentionOptions and HistoryRetentionLimit. 

The collection contains messages recorded at the job and the step level for all instances of the job. 

Because retrieving the data from the database and transmitting it to the client can be time-consuming, you can limit the number of records returned by using the maxRecords parameter. The returned collection is always sorted in descending order by the timestamp of the message, so if you limit the number of records to n, you will receive the most recent n messages. 

When the method returns foundRecords is set to the number of messages that actually exist for the job. User-interface applications therefore can first call the method with some reasonable value for maxRecords and then, if foundRecords exceeds this number, prompt the user before calling the method again to retrieve all records (this is the approach used by the adTempus Console). 

Each call only retrieves records that have been created since the last time the method was called, so calling the method frequently does not result in the same data being repeatedly sent from the server. 

If you are looking for specific messages, other approaches are better:

• Use the GetEvents method of the ExecutionHistoryItem or ExecutionHistoryStep to get the messages for a specific instance (execution) of the job, or for a specific step in a specific instance.

• Use the GetObjectsWhere method of the Scheduler object to filter records on the server.

ILogEvent